TeX 1995 July/TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO/systems/mac/sweet-tex/SwtUSInputPlusFlop097.cpt-hqx/###SwtUS_Input_Floppy0.97/RamStart 1.3.rsrc/HELP_259_Wondering.txt

Text File | 1987-11-20 | 3KB | 2 lines

# (decoded with TMPL 24282)
Text: 'If you were wondering╔╤╤╤╤╤╤╤╤╤╤╤╤╤╤╤╤╨This RAM disk disables Eject in the Finder's File menu and also will re-insert itself (once) if you do manage to eject it.  This is a very useful safety feature, since you can't push a RAM disk back in again.  Still, you can demolish the RAM disk by unmounting it (by dragging it to the trash), so please don't put your work files on it.System files are placed in the Unnamed (or Empty) folder to cut down on clutter.  If some files weren't copied, see if they are in the same folder as RamStart.  It won't see them if they're in any other folder, even if that folder is in RamStart's folder.RamStart remembers the amount of memory to keep for your programs to run in.  When it runs on a Macintosh with a different size of memory, such as a thin Mac or a Lisa, it will make a smaller or larger RAM disk.  If some memory is already set aside when it runs, such as for a debugger, RamStart will create a smaller RAM disk.  Allowing a debugger to be used was very helpful in getting RamStart to work, and it may help some of you.Unless you are using a debugger, don't press the mouse button until the dialog box appears.  Pressing earlier may ask a debugger to gain control at the beginning of the program, which you will regret if there isn't a debugger in memory.To force RamStart to run some other application than the Finder, or to get it to eject, etc., without having a Finder, name some other application "Finder" ╤ I have done this with the 4.1 MiniFinder ╤ or use a script, naming the application to be run.Sometimes you will need to think carefully how to arrange your files to fit them onto a RAM disk.  For Consulair's Mac C, I have tried several schemes.  Sometimes I patch the C compiler.  I have placed the System, Finder, Clipboard, Edit, C (ver 1.5), Link, and Exec on the RAM disk.  All other files, such as ASM, RMaker, Lister (a short PD program better than draft mode for listings, and smaller than Imagewriter), and all header files, on the disk in the internal drive.  I got an external drive, though, and it is a big help.RamStart uses the same driver ID (11) as the Assimilation Process RAM disk, which seems to be Apple's official RAM disk.  In the past, RamStart conflicted with AppleTalk; now, all RAM disk users should have the same (potential) conflicts.  RamStart will try to notice an older version's RAM disk if one is installed, but it may not succeed.  If you find that all you can make is a puny 6K RAM disk, this may be the problem.  You'll have to re-boot to get the memory back.HFS can be deadly slow when opening all files in a large directory.  To avoid this, use a script file, with the files named in alphabetical order, or run from an MFS floppy.  You can make an 800K MFS floppy by formatting it double-sided and then erasing it with an old (before 5.0) Finder.  Copy the files you want to the floppy -- don't drag the disk, as that will make it HFS again.  It won't hold quite as much, but RamStart will run much faster.Some extended memory boards don't clear all of memory when the system is reset, causing RamStart to think there is a RAM disk installed even though there is no driver for it.  The RAM disk is potentially recoverable, although RamStart does not do it yet.'